Payment Orchestration Architecture & Double-Entry Ledger Explorer

Active Mode: External USDC On-Chain Route Strict Decoupling of Policy, Ledger, and Provider Rails

External On-Chain USDC Transfer Lifecycle

When an internal Funding Instruction resolves to an external USDC payment, the system coordinates three distinct domains: Payment Orchestration & Routing (the brain), Treasury & Ledger Domain (the accountant), and Execution & Settlement Domain (the worker).

Decoupled System Architecture & Domain Boundaries

Introductory Overview: Below is the structural map connecting user triggers, routing decision policies, subledgers (Source ADA), and execution rails.

Orchestration Domain Ledger & ADA Domain Provider & Execution Domain

👛

Source ADA (Account of Digital Asset)

The platform app-level ledger account holding customer digital assets. Operates strict balance buckets: Available, Reserved, and Pending Outbound.

🌐

Destination Account / Rail Target

For external USDC routes, the destination is an on-chain blockchain wallet address (e.g. Polygon / Ethereum). For fiat routes, it is a linked bank account via Fedwire/ACH.

1. Payment Orchestration & Routing ⚡ Policy Brain

External Systems / UI Ingress

Initiates payment instruction requests into the platform.

Payment Instruction API State Coordinator

Manages instruction state machine (created → route_resolved → pending → confirmed).

Funding Router Engine Policy Evaluator

Scores candidates based on cost, latency, liquidity, and reliability telemetry.

2. Treasury & Ledger Domain 🛡️ Financial Truth

Treasury Position Calculator Deployable Guard

Computes exact deployable liquidity before route reservation.

Double-Entry Ledger Engine Append-Only

Translates operational events into balanced financial journal entries.

Accounts of Digital Asset (ADA) Subledger Buckets

Tracks Available, Reserved, Pending Outbound, and In-Transit buckets.

3. Execution & Settlement Domain 🚀 Rail Gateway

Provider Submitter Service Idempotent Worker

Issues execution calls to external providers (Circle API, Banking Gateways).

Circle API / Blockchain Rail External Network

Executes on-chain blockchain transfer or wire clearing.

Reconciliation Service Terminal Finality

Ingests webhooks and triggers terminal balance settlement in the ledger.

🔍

Click any component above to inspect details

Domain Inspection

Select any component card from the topology map to view its inputs, outputs, commands, and subledger hooks.

Interactive Route Decision & Scoring Math Engine

Tune policy parameters to see how the Router evaluates normalized scores across available execution rails.

Policy Profile: RP_MULTI_RAIL_ROUTER_V2

1. Adjust Policy Weights ($w$)

Cost Weight ($w_{cost}$): 0.30

Speed/Latency Weight ($w_{lat}$): 0.40

Liquidity Weight ($w_{liq}$): 0.15

Reliability Weight ($w_{rel}$): 0.15

2. Candidate Dynamic Inputs

Fedwire Wire Fee ($):

Polygon Gas Cost ($):

Scoring Formula:

Score = 100 × (w_cost·N_cost + w_lat·N_lat + w_liq·N_liq + w_rel·R)

Dynamic Candidate Route Scores Winner: RC_CIRCLE_ONCHAIN_A

Candidate Route	Cost	Speed	Reliability	Final Score

Architectural Event Catalog & Subledger Matrix

Filterable reference catalog of system events, commands, and ledger journal hooks.

Seq #	Event / Command Name	Phase	Sender → Receiver	State & Ledger Effect

Payment Orchestration Architecture Explorer